Hi,

It seems to me that this fix introduced some incorrect behaviour that was working correctly before. I recently updated the gamepads package to the latest version and noticed that all button keys have been renamed on iOS, which in itself is a breaking change, but I can understand that with this package being under development. So I did a remapping, and I realised that the left/right triggers on an Xbox Series controller are now acting as non-analog buttons, whereas previously were acting as analog ones. Also, when I tested my controller with other apps, the triggers were read as analog ones. Then I saw this update, in which it seems the whole status update logic has been reworked with the button keys remapped. In this code, the triggers are explicitly treated as non-analog buttons, so no wonder for the observed behaviour. I had to go back to version 0.1.2+2 of the gamepads_ios package to get back the analog behaviour, with which it is indeed working again.

Another missing feature I noticed is that the 'home' button on the Xbox controller isn't getting mapped with the latest version, while it did get mapped with the older version of the code (the 'options' and 'menu' buttons do work).

Also, the d-pad is now mapped as an analog button, whereas previously it was non-analog, which seems to be a better fit. Are there controllers on which the signal is actually analog? Also, the older version is working fine for me for the dead, getting -1, 0, 1 values across both axes.

I'm not sure what the required change would be for these issues, but from the older version working properly I guess it should be doable, and it should be fixed in order not to lose previously existing functionality.

By the way, can I ask what was the fundamental problem with the previous code logic that warranted the substantial reworking?

@wantroba could you please look into these issues?